System and method for provision of a second line service to a telecommunications device using mixed relationship numbers

ABSTRACT

A method and system for the leveraging a reserved relationship number by an SLS platform and/or SLS phone module for the purpose of performing special operations other than making an SLS call available for termination at a subscriber TD and/or a third party TD involve associating the SLS phone number of the subscriber, the primary number of the subscriber and a next set of instructions via a common reserved relationship number.

BACKGROUND

When a second line service (“SLS”) provider offers a method for routingcalls between an SLS subscriber's telecommunications device (“TD”) and athird party's TD, the method may involve using a common relationshipnumber associated to (1) the SLS number of the SLS subscriber, (2) theprimary phone number (or any phone number from which the SLS subscribercan make/receive a call) and (3) the primary phone number of a thirdparty (or any phone number from which the SLS subscriber canmake/receive a call). In the typical SLS scenario, an SLS based call orcommunication is initiated from the TD of an SLS subscriber, anddirected toward a particular third party or other final destination bythe SLS subscriber entering or selecting the relationship number,directly or indirectly. These SLS based call or communications arerouted to an SLS platform or server and then redirected by the SLSplatform or server to a third party TD that is identified or associatedwith the relationship number. More specifically, the SLS leverages therelationship number such that the SLS call is routed to the SLS platformor server. At the SLS platform or server, the combination of the phonenumber associated with the subscriber TD used to initiate the SLS basedcall, and the relationship number identified in the SLS call, allows theSLS platform or server to identify the third party or the ultimatedestination number. The SLS platform is then able to route the SLS basedcall to the third party number for call completion.

Despite the many benefits of a typical SLS, an SLS can provideadditional value to the subscriber if it could do more than leveragerelationship numbers for routing calls between an SLS subscriber's TDand a third party's TD. More specifically, an SLS could provideadditional value to the subscriber if it could leverage a new anddifferent type of relationship number for the purpose of performingspecial operations other than making an SLS call available fortermination at a subscriber TD or a third party TD. Accordingly, what isneeded is a system and method for this purpose.

SUMMARY OF THE DISCLOSURE

A method and system are described for the leveraging a reservedrelationship number by an SLS platform and/or SLS phone module for thepurpose of performing special operations other than making an SLS callavailable for termination at a subscriber TD and/or a third party TD.

In general, the operation of various embodiments of an SLS leveraging“Normal” relationship number are first described to provide an overallunderstanding of the SLS. Following this, the operation of variousembodiments of an SLS leveraging reserved relationship numbers arepresented.

An SLS system may operate in an environment in which an SLS platform isinterposed between a network serving as the primary service provider toa subscriber's TD and a network serving as the primary service providerto a third party TD. As such, a call originating from a third party TDand directed towards the SLS number associated with the TD of an SLSsubscriber, is routed by the receiving network to an SLS platform orserver for processing.

Upon receiving the call, the SLS platform queries a local database toidentify a relationship number that serves to map the primary number ofthe subscriber's TD to the combination of the third party calling numberand the subscriber's second line number. The call is then redirected tothe primary number of the subscriber's TD along with or in addition to,information that identifies the call as being directed to the SLSnumber. Once received by the subscriber's TD, the call setup iscompleted. Additional information may be included within the call signalsuch that an application running, associated with or resident on thesubscriber's TD can save the combination in a local database on thesubscriber's TD.

Advantageously, the relationship number so delivered to the subscriber'sTD can be used at a later time to initiate an SLS based call to a thirdparty. As a non-limiting example, dialing the third party's telephonenumber or otherwise initiating a call to the third party from the SLSapplication on the subscriber's TD can result in dialing or initiating acall to the relationship number for the third party. As such, when thecall enters the telephone network (such as the PSTN, MTSO, etc.) thecall is actually routed to the SLS platform. The SLS platform may thenuse the relationship number to identify the actual destination number ofthe third party and the SLS number that is attributed to being theoriginator of the call. Next, the SLS platform routes, bridges,transfers, initiates or otherwise establishes a completed communicationpath, or the delivery of a message from the originating TD to thedestination TD. As a non-limiting example, using the actual third partycalled number, the SLS platform may complete the second leg of the call.In certain embodiments, a call leg between a subscriber's TD and the SLSplatform may be completed using a session initiated protocol (“SIP”) sothat the data service provided by the primary service provider of thesubscriber device is used in lieu of a voice channel.

However, if a subscriber TD attempts to direct an SLS based call to athird party number the does not have an associated relationship number,the call may be directed to, or invoke the routing of the call to theSLS platform by placing the call to a new relationship number selectedby an SLS client application running on the subscriber's TD. In suchcase, the relationship number invokes the telecommunications network toroute the call to the SLS platform and the third party number isprovided to the SLS platform from the subscriber's TD. In otherembodiments, the new relationship number may be requested from the SLSplatform before making the call and then used by the subscriber's TD tomake the call. In either case, a new relationship number is used todirect the call from the subscriber's TD toward the third partydestination and to trigger the telecommunications network to route thecall to the SLS platform.

In the databases located at or accessible to the subscriber's TD and theSLS platform, the new relationship number maps the subscriber's primarynumber to the combination of the third party number and the subscriber'ssecond line number. The call is redirected by the SLS platform to thenumber associated with the third party TD and the call is completed.Advantageously, the new relationship number can be used at a later timeshould the subscriber desire to call the third party as previouslydescribed.

By associating the SLS phone number of the subscriber, the primarynumber of the subscriber and the phone number of a third party via acommon relationship number, SLS based calls can be directed to and froman SLS of a subscriber TD.

Understanding the general operation of the SLS, an SLS leveragingreserved relationship numbers can now be better understood. In general,this aspect of the various embodiments utilizes a different type ofrelationship number than has been previously presented. With regard to“Normal” relationship numbers, the translation of the specificinformation, e.g., which SLS phone number is calling and to which thirdparty telephone number the second leg of the SLS should be directed bythe SLS platform requires two pieces of information from the callsignal: the actual primary number associated with the subscriber TD andthe relationship number. The result of this is the ability for an SLSplatform and/or an SLS phone module to leverage a reserved relationshipnumber for the purpose of making an SLS call available for terminationat a subscriber TD and/or a third party TD

With regard to reserved relationship numbers, the SLS platform and/or anSLS phone module may leverage reserved relationship numbers for purposesother than making the call available for termination at subscriber TD110 through its SLS. As a non-limiting example, sometimes the call fromthe third party TD is received at the SLS platform and a query of acentral SLS database determines that the call was meant for the secondline number associated with subscriber TD; however, the SLS platform maynot be able to terminate the call at subscriber TD through its SLSbecause the subscriber does not answer the call, because the subscriberTD drops the call, etc. Despite these circumstances, the SLS platformmay leverage reserved relationship numbers stored in central SLSdatabase 116 to alert the SLS Module that a voice message has beendeposited for the subscriber.

In another non-limiting embodiment, receiving a call through an SLS froma third party TD when the call signal does not include the CLID or anyother data useful for identification of the phone number being used byand associated with the calling TD also involves leveraging a reservedrelationship number. In this embodiment, the telecommunications networkroutes the call based on the called number (the SLS phone numberassociated with the SLS subscriber). Ultimately, the telecommunicationsnetwork routes the call to SLS platform. Once the call reaches the SLSplatform, it cannot make a translation of the “Normal” relationshipnumber as described above because the call signal is missing necessaryinformation. Despite this set back, the SLS platform may maintain adatabase of reserved relationship numbers for each SLS subscriber. Thesereserved relationship numbers may be used to make a call between thesubscriber TD and the SLS platform like the “Normal” relationshipnumber; however, leveraging the reserved relationship number allows theSLS to perform special operations. For example, leveraging the reservedrelationship number may allow the SLS to include information in the callsignal indicating that the caller is unknown. In other non-limitingembodiments, leveraging the reserved relationship number may allow theSLS to route the call directly to voicemail server or inform the TD thata voicemail is waiting, etc.

Notably, it is envisioned by this disclosure that the “next set ofinstructions” associated with a reserved relationship number can be aone step set of instructions or it could be a complex multistep set ofinstructions. Additionally, it is envisioned by this disclosure that thesame reserved relationship number can be associated with a different“next set of instructions” depending on whether a call to that reservedrelationship number is from the SLS platform to the subscriber TD orfrom the subscribed TD to the SLS platform; the association may bedifferent if instead of a call, an SMS is directed to or from thereserved relationship number, etc. Although all these possibilities arenot described in detail within this disclosure, this should not limitthe scope of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

In the Figures, like reference numerals refer to like parts throughoutthe various views unless otherwise indicated. For reference numeralswith letter character designations such as “102A” or “102B”, the lettercharacter designations may differentiate two like parts or elementspresent in the same figure. Letter character designations for referencenumerals may be omitted when it is intended that a reference numeralencompass all parts having the same reference numeral in all figures.

FIG. 1 is a high level diagram illustrating exemplary components of asystem for providing an SLS to a subscriber TD.

FIG. 2 is a diagram of an exemplary network architecture for the systemof FIG. 1.

FIGS. 3A-3B illustrate exemplary data tables that may be leveraged by aredirection module of an SLS platform and an SLS module of a subscriberTD to provide a second line service to a user of subscriber TD.

FIGS. 3C-3D illustrate exemplary data tables that may be leveraged by aredirection module 117 of an SLS platform 115 and an SLS module of asubscriber TD to provide a second line service to a user of subscriberTD and allow the SLS to perform special operations

FIGS. 4A-4E collectively illustrate an exemplary method for implementingan SLS call between a third party TD and a TD associated with an SLSsubscriber using reserved relationship numbers.

FIGS. 5A-5B collectively illustrate an exemplary method for implementingan SLS, and its associated “next set of instructions,” between the SLSplatform and a TD associated with an SLS subscriber using a reservedrelationship numbers.

DETAILED DESCRIPTION

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any aspect described herein as “exemplary”is not necessarily to be construed as preferred or advantageous overother aspects.

In this description, the terms “application” and “app” may also includefiles having executable content, such as: object code, scripts, bytecode, markup language files, and patches. In addition, an “application”referred to herein, may also include files that are not executable innature, such as documents that may need to be opened or other data filesthat need to be accessed. Further, an “application” may be a completeprogram, a module, a routine, a library function, a driver, etc.

The term “content” may also include files having executable content,such as: object code, scripts, byte code, markup language files, andpatches. In addition, “content” referred to herein, may also includefiles that are not executable in nature, such as documents that may needto be opened or other data files that need to be accessed.

As used in this description, the terms “component,” “database,”“module,” “system,” and the like are intended to refer to acomputer-related entity, either hardware, firmware, a combination ofhardware and software, software, or software in execution. For example,a component may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer. By way of illustration, both anapplication running on a computing device and the computing device maybe a component.

One or more components may reside within a process and/or thread ofexecution, and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentsmay execute from various computer readable media having various datastructures stored thereon. The components may communicate by way oflocal and/or remote processes such as in accordance with a signal havingone or more data packets, e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems by way of the signal).

In this description, the terms “telecommunications device,”“communication device,” “wireless device,” “wireless telephone,”“wireless communication device” and “wireless handset” are usedinterchangeably. With the advent of third generation (“3G”) and fourthgeneration (“4G”) wireless technology, greater bandwidth availabilityhas enabled more portable computing devices with a greater variety ofwireless capabilities. Therefore, a telecommunications device (“TD”) mayinclude a cellular telephone, a pager, a PDA, a smartphone, a navigationdevice, a tablet personal computer (“PC”), or a hand-held computer witha wireless connection or link.

In this description, the terms “call” and “communication,” in their nounforms, envision any data transmission routed across a network from onedevice to another including, but not limited to, a voice transmission, atext message, a video message, a page, a data transmission, etc.

FIG. 1 is a high level diagram illustrating exemplary components of asystem 100 for providing an SLS to a subscriber TD 110. In general, anSLS based call can be originated by a subscriber TD 110 and directedtoward a non-subscriber or subscriber third party TD 120 or beoriginated by a non-subscriber or a subscriber third party TD 120 anddirected towards a subscriber TD 110. The typical subscriber TD 110 isassociated with a primary phone number assigned to it and provisionedand serviced by the subscriber's home mobile service provider (“primaryservice provider”) as is understood by one of ordinary skill in the art.A subscriber to an SLS offered through exemplary system 100 may receivecalls at the subscriber TD 110 that are originally directed to either ofthe primary phone number provided by the primary service provider or thesecondary phone number (“SLS phone number”) provided, serviced and orfacilitated by the SLS platform 115. It will also be appreciated that insome embodiments, the subscriber TD 110 may only include SLS operationand not include a primary number at all. In such embodiments, anycommunication between the TD 110 and the servicing network would occurover a data channel rather than a voice channel. In such embodiments,the TD 110 could actually be a computer device connected to theInternet. Yet in other embodiments, the TD 110 may include a minimalizedprimary number service that is greatly restricted. For instance, minimalmobile service only includes the ability to make a 911 emergency call.In some embodiments, one step above such limitation may be provided tothe TD 110 such that the TD 110 can only operate to exchange sufficientinformation with the network to establish an SLS call.

Notably, depending on the particular embodiment, the primary serviceprovider and the SLS platform, i.e., the second line service provider,may be the same provider or different providers. In embodiments wherethe primary service provider and the second line service provider aredifferent providers, the SLS subscriber may receive separate billingrecords from each provider. However, it is envisioned that certainembodiments where the primary service provider and the second lineservice provider are not one and the same may take advantage of sessioninitiated protocols (“SIP”) to simplify billing records for the user.

In general, any call directed to either of the primary phone number orthe SLS phone number are transmitted from a third party TD 120 to thesubscriber TD 110 by way of communications network 125. Notably,communications network 125 envisions any and all networks fortransmitting and terminating communications between TDs such as, but notlimited to, cellular networks, PSTNs, cable networks and the Internet.Methods for effecting the transmission of data across communicationsnetwork 125 from one device to another, including call setups,terminations and the like are understood by those of ordinary skill inthe art of data transmission and may include the use of protocols andstandards such as, but not limited to, signaling system seven (“SS7”)protocol suite, SIP, customized applications for mobile networksenhanced logic (“CAMEL”) or CAMEL Application Part (“CAP”), remoteoperations service element (“ROSE”), Voice Over IP (“VOIP”), etc.Notably, while the use of any particular protocol or communicationsstandard may be a novel aspect of a particular embodiment of the systemsand methods, it will be understood that the scope of the systems andmethods disclosed herein is not limited to the use of any particularprotocol or combination of protocols.

A call made from a third party TD 120 to the primary number associatedwith subscriber TD 110 is transmitted across communications network 125and routed to subscriber TD 110, as is understood in the art. The radiotransceiver 104, if the TD 110 is a portable and wireless device,enables the receipt and transmission of signals to and from subscriberTD 110. The call signal may include the calling line identification(“CLID”), i.e., the phone number being used by and associated with thirdparty TD 120 for the call, such that when the call is received atsubscriber TD 110 the CLID may be displayed for the benefit of the SLSsubscriber on display component 103.

Notably, although the exemplary embodiments described in the presentdisclosure use the CLID as an example of data that may be displayed forthe benefit of the user of a subscriber TD 110, it will be understoodthat any data associated with the third party TD 120, subscriber TD 110,SLS platform 115 or the like may be rendered for the benefit of the userof the system 100 and, as such, only describing that the CLID isdisplayed will not limit the scope of what is envisioned by thedisclosure. Moreover, it is envisioned that any data uniquely associatedwith a call to a primary number or an SLS phone number may be displayedfor the benefit of a SLS subscriber to the system 100.

Returning to the FIG. 1 illustration, a call made from a third party TD120 to an SLS phone number associated with subscriber TD 110 istransmitted across communications network 125. As one of ordinary skillin the art will understand, the communications network 125 routes thecall based on the dialed SLS phone number and routes the call to SLSplatform 115. This is the first leg of the SLS. SLS platform 115 thuseffectively intercepts the call, determines that the call was intendedfor subscriber TD 110 and then takes actions such that the call can beterminated at the subscriber TD 110. This is the second leg of the SLS.In this way, while a call directed to a primary number associated withsubscriber TD 110 is routed directly to subscriber TD 110, a calldirected to a second line number associated with subscriber TD 110 isroute to SLS platform 115 instead.

Once the call is received at SLS platform 115, a query of central SLSdatabase 116 by redirection module 117 determines that the call fromthird party TD 120 was meant for the second line number associated withsubscriber TD 110. Once the determination is made, redirection module117 processes the call and performs additional network functions suchthat the call is made available for termination at subscriber TD 110through its SLS.

Because the call may include data identifying it as a call to the SLSphone number associated with subscriber TD 110, SLS module 105intercepts the incoming call, or otherwise injects itself into the callprocessing activity for the call, and then leverages data stored inlocal SLS database 106 to render it in such a way that subscriber TD 110processes the call as an SLS call as opposed to a call directed at itsprimary phone number. The SLS module 105 is designed to work with radiotransceiver 104 and any stored or retrievable content in local SLSdatabase 106 to terminate a call to a SLS phone number, renderassociated data and provide services uniquely associated with the SLSphone number such as, but not limited to, dedicated voicemail,ringtones, caller ID, automated responses, etc.

Notably, it is envisioned by this disclosure that the SLS platform 115may leverage data stored in central SLS database 116 for purposes otherthan making the call available for termination at subscriber TD 110through its SLS. As a non-limiting example, sometimes the call fromthird party TD 120 is received at SLS platform 115 and a query ofcentral SLS database 116 determines that the call was meant for thesecond line number associated with subscriber TD 110; however, SLSplatform 115 may not be able to terminate the call at subscriber TD 110through its SLS because the subscriber does not answer the call, becausethe subscriber TD 110 drops the call, etc. Despite these circumstances,the SLS platform 115 may leverage data stored in central SLS database116 to alert the SLS Module 105 that a voice message has been depositedfor the subscriber.

A more detailed description of the exemplary method will be describedbelow relative to FIGS. 4-5, including exemplary methods for receiving acall from a third party TD 120 and making a call by way of the SLSplatform 115, and leveraging data stored in local SLS database 106and/or central SLS database 116 for purposes other than making an SLScall available for termination at subscriber TD 110 or third party TD120.

FIG. 2 depicts a diagram of exemplary network architecture 101 for thesystem 100 of FIG. 1. The exemplary network architecture 101 may includea subscriber TD 110 and a third party TD 120. Notably, although thethird party TD 120 is not illustrated to suggest that it is equippedwith SLS capability, it is envisioned that in some embodiments both thesubscriber TD 110 and the third party TD 120 may be SLS enabled.

As shown in the FIG. 2 illustration, an SLS platform 115 may beconnected to the subscriber TD 110 via a first provider network 201 andto the third party TD 120 via a second provider network 202, although itis envisioned that TDs 110 and 120 may be associated with a commonservice provider. One of ordinary skill in the art would recognize thatcommunications network 125 from FIG. 1 can be comprised of smallernetworks like first provider network 201 and second provider network202.

It is envisioned that the first provider network 201 and the secondprovider network 202 can be the same network. Additionally, it isenvisioned that the first provider network 201 and the second providernetwork can be operated, serviced, owned, etc. by the same or differentservice provider(s), and it is envisioned that either, or both, serviceproviders respectively associated with provider networks 201 or 202 mayfunction as both a primary service provider and/or an SLS provider for agiven subscriber TD 110 or third party TD 120. Furthermore, it isenvisioned that either or both of subscriber TD 110 and third party TD120 may be associated with a primary service provider and a separate SLSprovider.

Notably, depending on the particular embodiment, if subscriber TDs 110is situated outside of the locality serviced by its primary serviceprovider network then the first provider network 201 may be a secondaryservice provider network that is servicing the new locality. The same istrue for third party TD 120. Both of these “traveling” or “roaming”circumstances, and their associated systems and methods within thenetwork telecommunications architecture, are understood by those ofordinary skill in the art.

For exemplary purposes, the subscriber TD 110 is depicted as being SLSenabled and the third party TD 120 is depicted as not having a secondline service associated with it. Moreover, first provider network 201and the second provider network 202 are the same network in FIG. 2.Finally, first provider network 201 and the second provider network 202are depicted as networks that, at certain times and under certaincircumstances, may not make the CLID, or other data useful foridentification of the phone number being used by and associated with thecalling TD, available, reliably available, consistently available, etc.Despite what is depicted for exemplary purposes, other combinations ofprimary and secondary service provider networks connecting SLS platform115 to subscriber TD 110 and third party TD 120 are envisioned.

In the FIG. 2 illustration, it can be seen that the SLS platform 115 mayinclude an SLS server 205 configured to receive calls directed to andfrom an SLS phone number associated with subscriber TD 110. The SLSserver 205 includes a processor 209 and a memory 211 coupled to theprocessor 209. The memory 211 may include instructions for executing oneor more of the method steps described herein. Further, the processor 209and the memory 211 may serve as a means for executing one or more of themethod steps described herein. As indicated, the memory 211 may alsoinclude a redirection module 117 and a central SLS database 116.Notably, it should be understood that the term server 205 may refer to asingle server system or multiple systems or multiple servers. One ofordinary skill in the art will appreciate that the various serverarrangements may be selected depending upon computer architecture designconstraints and without departing from the scope of the invention.

As further illustrated in FIG. 2, the subscriber TD 110 may include aprocessor 208 and a memory 207 coupled to the processor 208. The memory207 may include instructions for executing one or more of the methodsteps described herein. Further, the processor 208 and the memory 207may serve as a means for executing one or more of the method stepsdescribed herein. As indicated, the memory 207 may also include an SLSmodule 105 and a local SLS database 106.

Illustrative embodiment of methods for providing an SLS to an SLSsubscriber will now be described in the context of the system andnetwork architecture described in FIGS. 1-2 and the exemplary datatables reflected in FIGS. 3A-3D. Specifically, three differentembodiments will be described: one embodiment describes receiving a callthrough an SLS from a third party TD 120 when the call signal does notinclude the CLID or any other data useful for identification of thephone number being used by and associated with the calling TD; thesecond and third embodiment describes leveraging data stored in localSLS database 106 and/or central SLS database 116 for purposes other thanmaking an SLS call available for termination at subscriber TD 110 orthird party TD 120.

With regard to the first embodiment, as previously stated, FIG. 1illustrates a call made from a third party TD 120 to an SLS phone numberassociated with subscriber TD 110. As one of ordinary skill in the artwill recall, the communications network 125 routes the call based on thecalled number (the SLS phone number associated with the SLS subscriber).Ultimately, communications network 125 routes the call to SLS platform115. SLS platform 115 effectively intercepts the call, determines thatthe call was intended for subscriber TD 110 and then takes actions using“relationship numbers” such that the call can be terminated at thesubscriber TD 110. Consequently, the first illustrative embodiment ofthe method involves leveraging two sets of intermediate phone numbers,one set of intermediate phone numbers for one leg of the SLS and theother for the second leg of the SLS, such that calls directed tosubscriber TD 110 ultimately terminate at TD 110 using the SLS.

FIGS. 3A-3B illustrate an exemplary data tables that may be leveraged bya redirection module 117 of an SLS platform 115 and an SLS module 105 ofa subscriber TD 110 to provide a second line service to a user ofsubscriber TD 110. Referring to FIGS. 3C-3D, illustrated are exemplarydata tables that may be leveraged by a redirection module 117 of an SLSplatform 115 and an SLS module 105 of a subscriber TD 110 to provide asecond line service to a user of subscriber TD 110 and allow the SLS toperform special operations. The Second Line Service Master ID Table 305and Subscriber Relationship ID Table 310 of FIG. 3A are stored in acentral SLS database 116 while the exemplary Subscriber Relationship IDTable 315 of FIG. 3B are stored in a local SLS database 106. Likewise,the Second Line Service Master ID Table 305 and Subscriber ReservedRelationship ID Table 320 of FIG. 3C are stored in a central SLSdatabase 116 while the exemplary Subscriber Reserved Relationship IDTable 325 of FIG. 3D are stored in a local SLS database 106. As such,some illustrative embodiments involve leveraging two sets ofintermediate phone numbers, the phone numbers related to the Second LineService Master ID Table 305 and the phone numbers related to theSubscriber Relationship ID Tables. Other illustrative embodimentsinvolve leveraging two sets of intermediate phone numbers, the phonenumbers related to the Second Line Service Master ID Table 305 and thephone numbers related to the Subscriber Reserved Relationship ID Tables.Notably, it is envisioned that in some illustrative embodiments threesets of intermediate phone numbers may be involved even though only twosets of intermediate phone numbers are actually leveraged for the firstand second leg of the SLS. Finally, it is envisioned that in someillustrative embodiments only one set of intermediate phone numbers maybe involved, specifically the phone numbers related to the SubscriberReserved Relationship ID Tables.

With regard to the first embodiment and to the leveraging of the firstset of intermediate phone numbers, specifically the phone numbersrelated to the Second Line Service Master ID Table 305, once the callreaches the SLS platform 115, an application running on redirectionmodule 117 makes a translation to complete this first leg of the SLS.The SLS platform 115 maintains a master list of SLS phone numbers thatare in service. In some embodiments, the SLS provider may be the owner,lessee, or assignee, etc. of these SLS phone numbers.

In the communications network 125, these SLS phone numbers route to theSLS platform 115, i.e., the SLS platform may be communicatively coupledwith communications network 125, and any of its component networks likefirst provider network 201 or second provider network 202, such that acall directed at the SLS phone number is ultimately routed to the SLSplatform. However, one of ordinary skill in the art will recognize that,depending on which provider network the SLS phone number is associated,a call directed at/directed from the SLS phone number is usually routedthrough its associated provider network before terminating at the SLSplatform. For example, in FIG. 2, if the SLS phone number is associatedwith first provider network 201, then any call direct at/directed fromthe SLS phone number is routed through first provider network 201regardless of the SLS phone number being owned, lease, or assigned, etc.by a separate SLS provider.

The SLS provider that manages the SLS platform 115 essentially has agroup of SLS phone numbers in inventory, and the SLS provider assignsthe SLS phone numbers to subscribers of the SLS. Regarding the SLSprovider's inventory of SLS phone numbers, one of ordinary skill in theart will recognize that the SLS phone numbers may be random andgenerally unrelated to each other, i.e., although the exemplary SLSphone numbers depicted in the FIG. 3A Second Line Service Master IDTable are sequential, it is envisioned that such is not the case in allembodiments.

Moreover, one of ordinary skill in the art will recognize that, althoughthe exemplary SLS phone numbers depicted in the FIG. 3A Second LineService Master ID Table 305 include a specific country code, area code,and seven digit directory number, it is envisioned that any countrycode, area code and directory number system known to those skilled inthe art is included within the scope of this disclosure. Additionally,it is envisioned that the SLS provider can maintain a large and diverseinventory of SLS phone numbers; each being associated with itsrespective provider network and, consequently, each routing through itsassociated provider network before terminating at the SLS platform 115.

Referring back to FIGS. 3A, the Second Line Service Master ID Table 305,the example Subscriber #1 has been issued SLS phone number1.770.555.0001. Other SLS subscribers in different situations and withdifferent circumstances are within the scope of this disclosure. Assuch, Subscriber #1 may choose to give out its SLS phone number to anyof its contacts.

With regard to the first embodiment and to the leveraging of the secondset of intermediate phone numbers, specifically the phone numbersrelated to the Subscriber Reserved Relationship ID Tables of FIGS.3C-3D, for each SLS subscriber a Subscriber Reserved Relationship IDTable 320 is also maintained. Referring to the Subscriber RelationshipID Table 320, the SLS provider has another list of dialable phonenumbers, i.e., reserved relationship numbers, which are maintained.These reserved relationship numbers are essentially “hidden numbers”that are used to make the second leg of the call between the subscriberTD 110 and the SLS platform 115.

In some embodiments, the SLS provider may be the owner, lessee, orassignee, etc. of these reserved relationship numbers. Like the SLSphone numbers, one of ordinary skill in the art will recognize that,depending on which provider network the reserved relationship numbersare associated, a call direct at/directed from the reserved relationshipnumbers are usually also routed through their associated providernetwork. For example, in FIG. 2, if the reserved relationship numbersare associated with first provider network 201/second provider network202, then any call direct at/directed from the relationship numbers isrouted through first provider network 201/second provider network 202regardless of the relationship number being owned, lease, or assigned,etc. by an SLS provider.

Concerning the Subscriber Reserved Relationship ID Table 320, one ofordinary skill in the art will understand that certain embodiments maynot formally distinguish one SLS subscriber's records from that ofanother via individual subscriber reserved relationship ID tables.Rather, as is understood in the art of database management and query, amore general relational database including records associated withmultiple SLS subscribers may be used to map SLS subscriber number andthe “next set of instructions” to a given reserved relationship number.As such, it will be understood by one of ordinary skill in the art thatthe description in this disclosure of exemplary embodiments that includeindividual subscriber reserved relationship ID tables are offered forillustrative purposes only and will not limit the scope of thedisclosure.

Additionally, concerning the use of reserved relationship numbers, it isenvisioned that certain reserved relationship numbers may be used for aplurality of SLS phone number and the “next set of instructions”combinations, i.e., in certain embodiments a given reserved relationshipnumber may not be unique to a given subscriber phone number and the“next set of instructions” combination. For example, in an illustrativenon-limiting embodiment, SLS subscribers D, E, F and G, may all havedatabase records that map reserved relationship number X to the “nextset of instructions” such as (J) “include information in the call signalindicating that the caller is unknown”, (K) “include information in thecall signal instructing the call to be immediately dropped”, (L) “routethe call immediately to voicemail” and (E) “inform the TD that avoicemail is waiting”, respectively. Notably, in this exemplaryscenario, the subscriber phone number and the “next set of instructions”combination G:E is meant to envision a case where G is associated withreserved relationship number such that G's TD can be informed that avoicemail is waiting on the SLS platform.

Like the SLS phone numbers, the SLS provider essentially has a group ofreserved relationship numbers in inventory, and the SLS provider assignsthe reserved relationship numbers as described above, and as describedin greater detail below. Regarding the SLS provider's inventory ofreserved relationship numbers, one of ordinary skill in the art willrecognize that the reserved relationship numbers may be random andgenerally unrelated to each other, i.e., although the exemplary reservedrelationship numbers depicted in the FIGS. 3C-3D Subscriber ReservedRelationship ID Tables are sequential, it is envisioned that such is notthe case in all embodiments.

Moreover, one of ordinary skill in the art will recognize that, althoughthe exemplary reserved relationship numbers depicted in the FIGS. 3C-3DSubscriber Reserved Relationship ID Tables include a specific countrycode, area code, and seven digit directory number, it is envisioned thatany country code, area code and directory number system known to thoseskilled in the art is included within the scope of this disclosure.Additionally, it is envisioned that the SLS provider can maintain alarge and diverse inventory of reserved relationship numbers; each beingassociated with its respective provider network and, consequently, eachrouting through its associated provider network when leveraged by theSLS.

Referring again to FIGS. 3C-3D and the Subscriber Reserved RelationshipID Tables, the example “next set of instructions” (1) “includeinformation in the call signal indicating that the caller is unknown”,(2) “route the call directly to voicemail server” and (3) “inform the TDthat a voicemail is waiting” have been associated with reservedrelationship numbers 1.678.444.0001, 1.678.444.0021 and 1.678.444.0031respectively. Other “next set of instructions” are within the scope ofthis disclosure. Notably, it is envisioned by this disclosure that the“next set of instructions” associated with a reserved relationshipnumber can be a one step set of instructions or it could be a complexmultistep set of instructions. The fact that three specific embodimentsof “next set of instructions” are described in this disclosure shouldnot be interpreted to limit the scope of the instructions that can beassociated with a reserved relationship number. Additionally, it isenvisioned by this disclosure that the same reserved relationship numbercan be associated with a different “next set of instructions” dependingon whether a call to that reserved relationship number is from the SLSplatform to the subscriber TD or from the subscribed TD to the SLSplatform; the association may be different if instead of a call, an SMSis directed to or from the reserved relationship number, etc. Althoughall these possibilities are not described in detail within thisdisclosure, this should not limit the scope of the disclosure.

As mentioned above, the reserved relationship numbers are “behind thescenes” numbers that are hidden from the SLS subscriber and any thirdparty calling the SLS subscriber through the SLS. This is accomplishedby an app running on SLS module 105 residing on subscriber TD 110. Inthe illustrative embodiment, SLS platform 115 has effectivelyintercepted the first leg of the SLS and determined that the call wasintended for subscriber TD 110 (this was described above). However,because the call signal does not include the CLID or any other datauseful for identification of the phone number being used by andassociated with third party TD 120, SLS platform 115 is unable tomap/query a relationship number (as distinct from the reservedrelationship number) for the SLS number and the third party phonenumber. As will be described in greater detail below, SLS platform 115takes an action that involves the reserved relationship number such thatthe call can be terminated at the subscriber TD 110. Essentially, byleveraging the reserved relationship number, an SLS provider maycontinue to insert itself into the middle of a call between a thirdparty TD 120 and a subscriber TD 110.

Returning to the FIGS. 3C-3D and the illustrative embodiment, Subscriber#1 associated with subscriber TD 110 already has mobile phone servicevia its primary service provider using mobile phone number1.408.544.1212. Subscriber #1 subscribes to an SLS provided by way ofSLS platform 115 and is assigned SLS phone number 1.770.555.0001. Thethird party uses TD 120 to place a call to the Subscriber #1's SLS phonenumber 1.770.555.0001. As described above, the call is routed to the SLSplatform 115. The SLS platform 115 accepts the call and determines thatthe call is for SLS phone number 1.770.555.0001, but because the callsignal does not include the CLID or any other data useful foridentification of the phone number being used by and associated withthird party TD 120, SLS platform 115 is unable to map/query arelationship number (as distinct from the reserved relationship number)for the SLS number and the third party phone number.

Consequently, the SLS platform 115 queries the reserved relationshipnumber in Subscriber Reserved Relationship ID Table 320 such that when1.770.555.0001 receives a call from an unknown third party phone number,the interaction with the subscriber TD 110 (having primary phone number1.408.544.1212) will use dialable reserved relationship number1.678.444.0001. This reserved relationship number was selected becausethe call signal does not include the CLID or any other data useful foridentification of the phone number being used by and associated withthird party TD 120 and, as a result, because SLS platform 115 is unableto map/query a relationship number using Subscriber Relationship IDTable 310. Notably, it is envisioned that a given reserved relationshipnumber, such as reserved relationship number 1.678.444.0001 in thepresent example, may be used as a reserved relationship number for manydifferent SLS subscribers. Moreover, it is envisioned that there can bean entire range of reserved relationship number, e.g., reservedrelationship number 1.678.444.0001-1.678.444.0010, that are associatedwith the same “next set of instructions.”

Now that the reserved relationship number 1.678.444.0001 has beenselected, the SLS platform 115 may proceed to establish the second legof the SLS—the call from the SLS platform 115 to the subscriber TD 110.The SLS platform 115 places the call to the subscriber TD 110. It isknown to those with ordinary skill in the art that methods forestablishing this second leg of the SLS include the use of protocols andstandards such as, but not limited to, SS7 protocol suite, SIP, CAMEL orCAP, ROSE, VOIP, etc. It is of course possible for the SLS platform 115to direct the call to the primary number 1.408.544.1212 of thesubscriber TD 110 using standard voice channels.

Returning to the illustrative embodiment, the CLID field for the callplaced from SLS platform 115 to subscriber TD 110 may contain aspecially encoded message for the SLS phone app running on SLS module105. In some embodiments, this CLID field may contain the relationshipnumber established by the SLS platform 115 (in this example,1.678.444.0001) and a message (in this example, “unknown caller”),separated by a dialable separator such as a “star” character. In otherembodiments, this CLID field may be populated with “unknown caller”only. Notably, it is envisioned that other embodiments may populate thisCLID field, or provide other metadata, that serves to triggerrecognition of the incoming call as a call directed to the SLS phonenumber of the SLS subscriber. As such, by describing the exemplaryembodiment to populate this CLID field with a combination of therelationship number and a message, the scope of the disclosure will notbe limited.

Having recognized that the incoming call is from the SLS platform 115,the SLS module 105 may store the combination of the reservedrelationship number 1.678.444.0001 with the associated “next set ofinstructions” in the local SLS database 106 if does not have thiscombination already stored. To complete the exemplary call, the SLSmodule 105 may cause the message “unknown caller” to be rendered ondisplay component 103 and rings the phone. Once the Subscriber #1answers, the SLS platform 115 connects the two legs of the SLS (leg 1represented by third party TD 120A to SLS platform 115 and leg 2represented by SLS platform 115 to subscriber TD 110) by methods knownand understood by those of ordinary skill in the art oftelecommunications. As non-limiting examples, the calls can be connectedvia a forward or a bridge, as well as other technologies known to thosewith ordinary skill in the art. Notably, it is envision by thisdisclosure that the call could be routed through the intermediate SLSplatform 115 as a way of enabling the SLS between the third party TD 120and the subscriber TD 110.

Notably, in the example, the combination of the reserved relationshipnumber 1.678.222.0001 and the “next set of instructions” is now storedin the central SLS database 116 at SLS platform 115 and also in thelocal SLS database 106 in subscriber TD 110. As one of ordinary skill inthe art will recognize, the importance of the reserved relationshipnumber is that it may also provide a mechanism by which the SLS platform115 may intercept SLS calls originating from subscriber TD 110 (in muchthe same way as the SLS phone number provides a mechanism by which theSLS platform may intercept SLS calls originating from the third party TD120).

With regard to the second illustrative embodiment, suppose Subscriber #1associated with subscriber TD 110 already has mobile phone service viaits primary service provider using mobile phone number 1.408.544.1212.Subscriber #1 subscribes to an SLS provided by way of SLS platform 115and is assigned SLS phone number 1.770.555.0001. However, instead ofthird party TD 120 placing a call to the Subscriber #1's SLS phonenumber 1.770.555.0001 (as described in the first illustrativeembodiment), SLS platform 115 has received a call, signal, trigger orcommand to inform subscriber TD 110 that the subscriber has a voicemailwaiting for it.

Consequently, the SLS platform 115 queries the reserved relationshipnumber in Subscriber Reserved Relationship ID Table 320 such that when1.770.555.0001 has a voicemail waiting for it, the interaction with thesubscriber TD 110 (having primary phone number 1.408.544.1212) will usedialable reserved relationship number 1.678.444.0031. Notably, it isenvisioned that a given reserved relationship number, such as reservedrelationship number 1.678.444.0031 in the present example, may be usedas a reserved relationship number for many different SLS subscribers.Moreover, it is envisioned that there can be an entire range of reservedrelationship number, e.g., reserved relationship number1.678.444.0031-1.678.444.0040, that are associated with the same “nextset of instructions.”

Now that the reserved relationship number 1.678.444.0031 has beenselected, the SLS platform 115 may proceed to establish a call from theSLS platform 115 to the subscriber TD 110. The SLS platform 115 placesthe call to the subscriber TD 110. It is known to those with ordinaryskill in the art that methods for establishing this call include the useof protocols and standards such as, but not limited to, SS7 protocolsuite, SIP, CAMEL or CAP, ROSE, VOIP, etc. It is also envisioned thatshort message service (“SMS”) protocol, multimedia messaging service(“MMS”) protocol, and/or other protocols may be used by someembodiments. It is of course possible for the SLS platform 115 to directthe call to the primary number 1.408.544.1212 of the subscriber TD 110using standard voice channels.

Returning to the illustrative embodiment, supposing that the call usesan MMS, the SLS Platform may include information in the call signal(either the voice channel, the data channel, within the MMS itself, inthe CLD, etc.) from the SLS platform 115 to subscriber TD 110 for theSLS phone app running on SLS module 105. In some embodiments, this CLIDfield may contain the reserved relationship number established by theSLS platform 115 (in this example, 1.678.444.0031) and a message (inthis example, “voicemail waiting”), separated by a dialable separatorsuch as a “star” character. In other embodiments, the SLS module 105 maycause the subscriber TD 110 to be notified of the pending voicemailthrough a pop up notification via the SLS application running on the TD,via the operating system running on the TD, via another applicationrunning on the phone, etc. Notably, it is envisioned that otherembodiments may include information in the call signal, or provide othermetadata, that serves to trigger recognition of the pending voicemail.As such, by describing the exemplary embodiment as populating a messagewith a combination of the reserved relationship number and a message,the scope of the disclosure will not be limited.

In other non-limiting embodiments, the subscribed TD 110, havingrecognized that the incoming MMS is from the SLS platform 115, the SLSmodule 105 may store the combination of the reserved relationship number1.678.444.0031 with the associated “next set of instruction” in thelocal SLS database 106 if does not have this combination already stored.To complete the exemplary call, the SLS module 105 may cause the message“voicemail waiting” to be rendered on display component 103 and ringsthe phone. Notably, in the example, the combination of the reservedrelationship number 1.678.222.0031 and the “next set of instructions,”inform the TD that a voicemail is waiting, is now stored in the centralSLS database 116 at SLS platform 115 and also in the local SLS database106 in subscriber TD 110.

With regard to the third illustrative embodiment, suppose Subscriber #1desires to listen to a pending voicemail. Subscriber #1 must initiate acommunication with the voicemail server from its SLS phone number1.770.555.0001. Notably, it is envisioned by this disclosure that theSLS platform 115 may house a voicemail server for voicemails left forSLS subscribers. Those of ordinary skill in the art will understand howthese voicemail servers operate and how these voicemail servers may beintegrated into the system 100 and/or 101 for providing an SLS to asubscriber TD 110.

Like the Subscriber Reserved Relationship ID Table 320 maintained oncentral SLS database 116, Subscriber TD 110 also maintains a SubscriberRelationship ID Table 325 in local SLS database 106. It is envisioned bythis disclosure that these Subscriber Relationship ID Tables can besynchronized, updated, reconciled, etc. with one another such that eachtable reflects substantially similar and up-to-date associationinformation for the reserved relationship numbers. It is also envisionedby this disclosure that these Subscriber Relationship ID Tables may bepurposely kept different from one another. To place calls from its SLSphone number, Subscriber #1 may use the SLS phone app of SLS module 105to dial, as a non-limiting example of one potential embodiment, thereserved relationship number. Notably, one of ordinary skill in the artwill recognize that the SLS phone app may have a button, short cut, orother previously programmed trigger for purposes of dialing the reservedrelationship number without the subscriber having to directly dialand/or know the reserved relationship number.

In one non-limiting example, Subscriber #1 causes the SLS module 105 todial the reserved relationship number 1.678.444.0031 when it selects a“call voicemail” button in the SLS phone app (not depicted in the FIGS).As described more fully above, the reserved relationship number1.678.444.0031 is reflected in the Private Reserved Relationship IDTables 320 and 325 as being associated with the “next set ofinstructions” “route the call directly to voicemail server”. Notably, itis envisioned by this disclosure that the “next set of instructions” mayroute the call to voicemail on a third party network device, on adatabase communicatively coupled to the communications network 125, etc.

Regardless of which embodiment causes the SLS module 105 to select fromSubscriber Reserved Relationship ID Table 325 in local SLS database 106the reserved relationship number 1.678.444.0021, the SLS module 105dials the reserved relationship number 1.678.444.0021. The SLS module105 may indicate to the SLS subscriber via display 103 that it iscalling “voicemail”, but instead it calls the reserved relationshipnumber 1.678.444.0021. By calling this reserved relationship number, thecommunications network 125 routes the call to the SLS platform 115instead of subscriber TD communicating directly with the voicemailserver, for example. This is the first leg of the SLS.

When the SLS platform 115 processes this first leg of the SLS, it mayrecognize that the calling number is the SLS subscriber's primary number1.408.544.1212 (which is associated with the subscriber's SLS phonenumber 1.770.555.0001) and the called number is the reservedrelationship number 1.678.444.0021. Querying the Subscriber ReservedRelationship ID Table 320 in central SLS database 116, the redirectionmodule 117 may apply the following logic: “when primary number1.408.544.1212 calls reserved relationship number 1.678.444.0021, it isactually SLS phone number 770.555.0001 wanting to access its voicemail.”The SLS platform 115 may then follow that logic and complete the secondleg of the SLS by establishing a communication with the voicemailserver. Notably, it is envisioned by this disclosure that the SLSplatform 115 may establish the communication with the voicemail serverby dialing a phone number associated with the voicemail server using theSLS number 1.770.555.0001. It is known to those with ordinary skill inthe art that methods for establishing this communication include the useof protocols and standards such as, but not limited to, SS7 protocolsuite, SIP, CAMEL or CAP, ROSE, VOIP, etc.

Notably, in completing the second leg of the SLS and connecting the twolegs (in much the same way as described above for SLS calls originatingfrom a third party), the SLS platform 115 may modify the CLID fielddisplayed for the benefit of the voicemail server to be something otherthan the SLS phone number 1.770.555.0001 from which the second leg ofthe SLS is made. As a non-limiting example, it is envisioned that theSLS platform 115 may modify the CLID field to be the primary number ofsubscriber TD 110.

As described above, it is envisioned that another SLS subscriber (forexample, Subscriber #2 having SLS phone number 1.770.555.0002) couldalso initiate the first leg of an SLS call by using the reservedrelationship number 1.678.444.0021. In this situation, the SLS platform115 could direct the second leg of the SLS to a different voicemailserver associated with Subscriber #2 or an entirely different “next setof instructions” may be performed by the SLS platform 115. As isdescribed above, the encoded voicemail server phone number called by theSLS platform 115 for the second leg of the call is derived from thecombination of the SLS phone number and the reserved relationship numberand is part of the “next set of instructions” to be performed.

FIGS. 4A-4E collectively illustrate an exemplary method 400 forimplementing an SLS call between a third party TD, such as third partyTD 120, and a TD associated with an SLS subscriber, such as subscriberTD 110, using reserved relationship number. Method 400 takes intoconsideration circumstances when the call signal from the third party TD120 does not include the CLID or any other data useful foridentification of the phone number being used by and associated withthird party TD 120 for the call. At block 402, a call is directed to andreceived by an SLS platform 115. Notably, the call is envisioned to beany communication over communications network 125 that is directed toSLS platform 115, regardless of whether such communication originatesfrom a subscriber TD 110 or a third party TD 120. One of ordinary skillin the art will recognize that a communication may include the use ofprotocols and standards such as, but not limited to, SS7 protocol suite,SIP, CAMEL or CAP, ROSE, VOIP, etc.

Next, at decision block 404, the SLS platform 115 determines whether thecall originated from a third party TD 120 directed to an SLS subscriber,i.e., whether a third party has dialed an SLS phone number associatedwith an active SLS subscriber. If the communication was not a call thatoriginated from a third party TD 120, then the “no” branch is followedto block 432 of FIG. 4D. If the call did, in fact, originate from athird party TD 120, then the “yes” branch is followed to block 405.Notably, if a call is directed to the SLS platform 115, one of ordinaryskill in the art will recognize that the communication was either a callto an SLS phone number (if dialed by a third party TD 120), a call to arelationship number (if originating from an SLS client of a subscriberTD 110), or a data communication originating from an SLS client of asubscriber TD 110 (not depicted in the figures).

At block 405, the SLS platform 115 attempts to obtain the phone numberbeing used by third party TD 120 to call the SLS phone number associatedwith subscriber TD 110. If at decision block 406, the SLS platform 115is unable to obtain the phone number being used by third party TD 120because the call signal from the third party TD 120 does not include theCLID or any other data useful for identification of the phone numberbeing used by and associated with third party TD 120 to call the SLSphone number associated with subscriber TD 110, then the “no” branch isfollowed to block 452 of FIG. 4B. If the SLS platform 115 is able tosuccessfully obtain the phone number being used by third party TD 120 tocall the SLS phone number associated with subscriber TD, then the “yes”branch is followed to block 407.

At block 407, the SLS platform 115 queries central SLS database 116 forthe phone number being used by third party TD 120 in association withthe SLS phone number that caused the call to be routed to the SLSplatform 115. If at decision block 408, the SLS platform 115successfully queries the phone number being used by third party TD 120and SLS phone number combination, then the “yes” branch is followed toblock 422 of FIG. 4C. If the phone number being used by third party TD120 and SLS phone number combination are not successfully queried, thenthe “no” branch is followed to block 410.

At block 410, the SLS platform 115 may associate a new relationshipnumber with the phone number being used by third party TD 120 to makethe call, the SLS subscriber's primary phone number and the subscriber'sSLS phone number. At block 412, the central SLS database 116 is updatedto include the newly created record—the phone number being used by thirdparty TD 120 to make the call is listed as a contact of the SLSsubscriber in the Subscriber Relationship ID Table 310. At block 414, acall is established between the SLS platform 115 and the subscriber TD110. In some non-limiting embodiments of block 414, the SLS platform 115initiates the call through the communication network 125's voice channelwith the subscriber TD 110 by dialing its primary phone number from therelationship number of block 410. In other non-limiting embodiments ofblock 414, the subscriber's TD 110 initiates the call through thecommunication network 125's voice channel with the SLS platform 115 bydialing the relationship number of block 410 from the subscriber TD110's primary phone number after receiving a data communication from theSLS platform 115 with information containing the relationship number ofblock 410 and instructions to initiate the call (again, one of ordinaryskill in the art will recognize that a communication may include the useof protocols and standards such as, but not limited to, SS7 protocolsuite, SIP, CAMEL or CAP, ROSE, VOIP, etc). In certain non-limitingembodiments of block 1414, the SLS platform 115 may populate the CLIDfield of the call between it and the subscribers TD 110 with acombination of the newly assigned relationship number and the phonenumber being used by third party TD 120 to make the call.

At block 416, the local SLS database 106 updates to include the newlyassigned relationship number in association with the phone number beingused by third party TD 120 to make the call. At block 418, the phonenumber being used by third party TD 120 to make the call is displayed tothe SLS subscriber and the SLS subscriber is alerted to the incomingcall. Notably, it is envisioned that displaying the phone number beingused by third party TD 120 to make the call may include rendering theCLID field itself, rendering a picture of the third party, rendering aname, etc. as is understood by those with ordinary skill in the art ofgraphical user displays and interfaces. At block 420, the call fromblock 402 is bridged with the call from block 414 resulting in an activecall between third party TD 120 and subscriber TD 110. One of ordinaryskill in the art will recognize that there are many systems and methodsknown and understood for bridging or connecting a plurality of separatecalls (the legs of the SLS); consequently, this disclosure is notlimited by the used example “bridged.”

It is envisioned that the steps taken at block 418 of the method 400 maydiffer in some embodiments. For instance, when a third party TD 120'scall to an SLS phone number is received at the SLS platform 115, and thephone number being used by third party TD 120 to make the call is notyet associated with a relationship number, the SLS platform 115 mayassign a next relationship number as described relative to blocks410-412 then establish a call with the subscriber TD 110 as described in414. The SLS module 105 of the subscriber TD 110, having no record ofthe new relationship number in its local database 106, may display thecalling number as “unknown caller” on the display of the subscriber TD110. At the same time, the SLS module 105 may establish a dataconnection over communications network 125 with the SLS platform 115 forthe purpose of acquiring the third party calling number associated withthe new relationship number. Once the phone number being used by thirdparty TD 120 to make the call is acquired, the SLS module 105 may updatethe local database 106 and change the display from “unknown caller” tothe phone number being used by third party TD 120 to make the call.

Turning now to FIG. 4B, if the “no” branch is followed from block 406 ofFIG. 4A, at decision block 452 the SLS platform 115 queries the centralSLS database 116 for the reserved relationship number that maps to thecombination of the subscriber's SLS phone number and the “next set ofinstructions” “include information in the call signal indicating thatthe caller is unknown”.

At block 454, a call is established between the SLS platform 115 and thesubscriber TD 110. In some non-limiting embodiments of block 454, theSLS platform 115 initiates the call through the communication network125's voice channel with the subscriber TD 110 by dialing its primaryphone number from the reserved relationship number of block 452. Inother non-limiting embodiments of block 454, the subscriber's TD 110initiates the call through the communication network 125's voice channelwith the SLS platform 115 by dialing the reserved relationship number ofblock 452 from the subscriber TD 110's primary phone number afterreceiving a data communication from the SLS platform 115 withinformation containing the reserved relationship number of block 452 andinstructions to initiate the call. In certain non-limiting embodimentsof block 454, the SLS platform 115 may populate the CLID field of thecall between it and the subscribers TD 110 with a combination of theassigned reserved relationship number and a message indicating “unknowncaller”.

It is envisioned that in some embodiments of block 454 an SLS module 105may recognize that an incoming call is from the SLS platform 115 byvirtue of the call originating from a reserved relationship number. Atblock 456, a message is displayed to the SLS subscriber and the SLSsubscriber is alerted to the incoming call. At block 460, the call fromblock 402 is bridged with the call from block 454 resulting in an activecall between third party TD 120 and subscriber TD 110. One of ordinaryskill in the art will recognize that there are many systems and methodsknown and understood for bridging or connecting a plurality of separatecalls (the legs of the SLS); consequently, this disclosure is notlimited by the used example “bridged.” It is envisioned that, if thesubscriber elects not to answer a call to the SLS phone number, the SLSmodule 105 in some non-limiting embodiments may use a voicemail serviceor message service in response to the unanswered call. That is, it isenvisioned that an SLS service may provide features and servicesdedicated to the SLS subscriber and separate from similar features andservices associated with the subscriber's primary number.

Turning now to FIG. 4C, if the “yes” branch is followed from decisionblock 408 of FIG. 4A, at block 422 the SLS platform 115 queries thecentral SLS database 116 for the relationship number that maps to thecombination of the phone number being used by third party TD 120 andsubscriber's SLS phone number. At block 423, the SLS platform 115determines if it should modify the relationship number of block 422based on the location of the subscriber TD 110. If at decision block 423the SLS platform 115 determines that it should modify the relationshipnumber of block 422, then the “yes” branch is followed to block 410 ofFIG. 4A. If at decision block 423 the SLS platform 115 determines thatit should not modify the relationship number of block 422, then the “no”branch is followed to block 424.

At block 424, a call is established between the SLS platform 115 and thesubscriber TD 110. In some non-limiting embodiments of block 424, theSLS platform 115 initiates the call through the communication network125's voice channel with the subscriber TD 110 by dialing its primaryphone number from the relationship number of block 422. In othernon-limiting embodiments of block 414, the subscriber's TD 110 initiatesthe call through the communication network 125's voice channel with theSLS platform 115 by dialing the relationship number of block 422 fromthe subscriber TD 110's primary phone number after receiving a datacommunication from the SLS platform 115 with information containing therelationship number of block 422 and instructions to initiate the call.In certain non-limiting embodiments of block 414, the SLS platform 115may populate the CLID field of the call between it and the subscribersTD 110 with a combination of the assigned relationship number and thephone number being used by third party TD 120 to make the call.

It is envisioned that in some embodiments of block 424 an SLS module 105may recognize that an incoming call is from the SLS platform 115 byvirtue of the call originating from a relationship number. At block 426,the phone number being used by third party TD 120 to make the call isdisplayed to the SLS subscriber and the SLS subscriber is alerted to theincoming call. Notably, it is envisioned that displaying the phonenumber being used by third party TD 120 to make the call may includerendering the CLID itself, rendering a picture of the third party,rendering a name, etc. as is understood by those with ordinary skill inthe art of graphical user displays and interfaces. In certainnon-limiting embodiments of block 426, the information populated by theSLS platform 115 in the CLID field of the call between SLS platform 115and the subscribers TD 110 may cause the SLS module 105 to handle thecall and display the associated third party CLID for the benefit of thesubscriber.

At block 430, the call from block 402 is bridged with the call fromblock 424 resulting in an active call between third party TD 120 andsubscriber TD 110. One of ordinary skill in the art will recognize thatthere are many systems and methods known and understood for bridging orconnecting a plurality of separate calls (the legs of the SLS);consequently, this disclosure is not limited by the used example“bridged.” It is envisioned that, if the subscriber elects not to answera call to the SLS phone number, the SLS module 105 in some non-limitingembodiments may use a voicemail service or message service in responseto the unanswered call. That is, it is envisioned that an SLS servicemay provide features and services dedicated to the SLS subscriber andseparate from similar features and services associated with thesubscriber's primary number.

Turning now to FIG. 4D, if the “no” branch is followed from block 404 ofFIG. 4A, at decision block 432 the SLS platform 115 determines if thecall was directed to a relationship number. Notably, if the call isdirected to a relationship number, then it must have originated from asubscriber TD 110. If the call was not directed to a relationshipnumber, the “no” branch is followed to block 442 of FIG. 4E. If,however, the call was routed to the SLS platform 115 because it wasdirected to a relationship number then the “yes” branch is followed toblock 434.

At block 434, the central SLS database 116 is queried for the thirdparty TD 120's phone number in combination with the relationship numberthat was dialed by subscriber TD 110 that resulted in the call routingto the SLS platform 115 and the SLS phone number and the SLSsubscriber's primary phone number. At block 436, the SLS platform 115determines the third party TD 120's phone number with which therelationship number and the SLS subscriber's primary phone numbercombination is associated. At block 438, a call is established betweenthe SLS platform 115 and the third party TD 120. In some non-limitingembodiments of block 438, the SLS platform 115 initiates the callthrough the communication network 125's voice channel with the thirdparty TD 120 by dialing the third party TD 120's phone number determinedin block 436. In some non-limiting embodiments of block 438, the SLSplatform 115 may populate the CLID field of the call between it and thethird party TD 120 with the SLS phone number of subscriber TD 110. Inother non-limiting embodiments of block 438, the SLS platform 115 maypopulate the CLID field of the call between it and the third party TD120 with the primary phone number of subscriber TD 110.

At block 440, the call from block 402 is bridged with the call fromblock 438 resulting in an active call between subscriber TD 110 andthird party TD 120. One of ordinary skill in the art will recognize thatthere are many systems and methods known and understood for bridging orconnecting a plurality of separate calls (the legs of the SLS);consequently, this disclosure is not limited by the used example“bridged.” It is envisioned that, if the third party elects not toanswer a call to it from SLS, the SLS platform 115 in some non-limitingembodiments may continue the bridge even when the call from block 438 isrouted to its voicemail service or message service.

Turning now to FIG. 4E, if the “no” branch is followed from block 432 ofFIG. 4D, at decision block 442 the SLS platform 115 determines that thecommunication is a data communication over communications network 125that originated from an SLS client of a subscriber TD 110. If not, thenit is assumed that it was an errant communication and the “no” branch isfollowed to block 444 and the communication is disconnected. If thecommunication did originate from a SLS client, i.e., an SLS module 105in a subscriber TD 110 associated with a subscriber to the SLS service,then the “yes” branch is followed to block 446. It is envisioned thatthe communication from an SLS client application to an SLS platform maybe of any protocol suitable for communicating over communicationsnetwork 125 including the use of protocols and standards such as, butnot limited to, SS7 protocol suite, SIP, CAMEL or CAP, ROSE, VOIP, etc.

At block 446, it is deduced by the SLS platform 115 that the subscriberassociated with the calling SLS client desires to use the SLS service tocall third party TD 120's phone number with which no relationship numberhas been previously associated (such as would occur at block 410) TheSLS module 105 has provided the request for the new relationship number,along with the third party number it desires to call, to the SLSplatform 115 via the data communication. The central SLS database 116 isqueried at block 446 to determine the next available relationship numberfor the subscriber's given SLS phone number.

The SLS platform 115 may associate a new relationship number with thesubscriber's SLS phone number, the SLS subscriber's primary phone numberand the third party TD 120's phone number. It is envisioned that the SLSmodule 105 may communicate with the SLS platform 115 in some embodimentsto obtain a relationship number for a third party that has notpreviously been called via a session-based protocol such as, but notlimited to, an unstructured supplementary services data (“USSD”)protocol. As is understood in the art of telecommunications protocols, agateway such as a USSD gateway may be used to route messages from asignaling network to service applications and back. In this way, certainembodiments of an SLS module 105 may communicate with an SLS platform115 to designate and acquire a relationship number to a third party whohas not been called by the subscriber before via the SLS.

Moreover, USSD is offered herein for exemplary purposes and is not meantto limit the type of communications protocol that may be used by certainembodiments. For example, it is envisioned that short message service(“SMS”) protocol, multimedia messaging service (“MMS”) protocol, and/orother protocols may be used by some embodiments. It is envisioned thatan IP-based interaction over the TD's data service may be used by someembodiments. As would be recognized by one of ordinary skill in the art,use of session based protocols or other communication protocols mayminimize temporal delays in allocating and acquiring relationshipnumbers between an SLS module 105 and an SLS platform 115. In fact, itis anticipated that any mechanism that can be used to establish acommunication path between the SLS module 105 and the SLS platform 115for the purposes of supporting the SLS can be utilized. This may includeany of the varieties of cellular data, WiFi, Bluetooth technologies,proprietary wireless or wired technologies, etc. Such channels can beused in setting up the relationship databases, sharing informationbetween the SLS module 105 and the SLS platform 115, initiating voicecommunication establishment from the TD 110 to the SLS platform 115, theTD 110 requesting the SLS platform 115 to place a call to a third partyTD 120, etc.

At block 448, the determined next available relationship number isreturned to the SLS module 105 of the subscriber TD 110. At block 450,the central SLS database 116 is updated with the new relationshipnumber. The new relationship number is now associated in the central SLSdatabase 116 with the subscriber's SLS phone number, the SLSsubscriber's primary phone number and the third party TD 120's phonenumber. Notably, after blocks 448 and/or 450, the method 400 may returnto the start of method 400 at block 402 as the SLS module 105 of thesubscriber TD 110 has acquired a new relationship number. Consequently,using the newly acquired relationship number may essentially start overthe method 400 with the SLS platform 115 receiving the call. If so, themethod 400 would follow to FIG. 4D where the call was recognized as thesubscriber TD 110 having placed a call to the new relationship number.

Turning now to FIGS. 5A-5B, these figures collectively illustrate anexemplary method 500 for implementing an SLS, and its associated “nextset of instructions,” between SLS platform 115 and a TD associated withan SLS subscriber, such as subscriber TD 110, using a reservedrelationship number. At block 502, a call, signal, trigger or command isdirected to and received by an SLS platform 115. Notably, the call,signal, trigger or command is envisioned to originate from within theSLS platform 115, i.e., from its own internal software or hardware, orfrom an external network element that is communicatively coupled to theSLS platform through communications network 125, e.g., a third partyvoicemail server, a third party TD 120, etc. One of ordinary skill inthe art will recognize that a call, signal, trigger or command from anexternal network element may include the use of protocols and standardssuch as, but not limited to, SS7 protocol suite, SIP, CAMEL or CAP,ROSE, VOIP, etc. Additionally, it is envisioned by this disclosure thatthe call, signal, trigger or command may prompt the SLS platform 115that the “next set of instructions” associated with a reservedrelationship number is need to be performed, e.g., (1) a voicemailserver transmits a signal to the SLS platform 115 prompting the SLSplatform that the “next set of instructions” “inform the TD that avoicemail is waiting” is needed to be performed, or (2) a subscriber TD110 initiates a call with the SLS platform 115 prompting the SLSplatform that the “next set of instructions” “route the call directly tovoicemail server” (to be described more fully below).

Next, at decision block 504, the SLS platform 115 determines whether thecall, signal, trigger or command originated from a subscriber TD 110,i.e., whether a subscriber TD 110 has dialed a reserved relationshipnumber associated with its SLS. If the communication was not a call,signal, trigger or command that originated from a subscriber TD 110,then the “no” branch is followed to block 512 of FIG. 5B. If the call,signal, trigger or command did, in fact, originate from a subscriber TD110, then the “yes” branch is followed to block 506. At block 506 theSLS platform 115 queries the central SLS database 116 for the “next setof instructions” that maps to the combination of the reservedrelationship number at which the subscriber TD 110 directed the call andthe subscriber's SLS phone number.

At block 508, the SLS platform 115 performs the “next set ofinstructions” queried from block 506. Notably, it is envisioned by thisdisclosure that performance of these instructions may involve one ormultiple steps and that these steps may involve one or more pieces ofhardware/software separate and distinct from the SLS platform 115. Thoseof ordinary skill in the art will recognize that, depending on thenature of the “next set of instructions” associated with the reservedrelationship number, e.g., instructions involving networking and theinternet, instructions involving physical processes like printing,instructions involving complex search algorithms and instructionsinvolving third party software, multiple components of the SLS platform115 and/or other communicatively coupled pieces of hardware may be usedto perform and/or process the “next set of instructions.” Finally, it isalso envisioned by this disclosure that the possible combinations ofreserved relationship numbers and “next set of instructions” are notlimited by the three specific examples described herein. As anon-limiting example, the SLS module 105 may perform all the steps,functions, processing, etc. related to the “next set of instructions”“route the call directly to voicemail server”.

Turning now to FIG. 5B, if the “no” branch is followed from block 504 ofFIG. 5A, at decision block 512 the SLS platform 115 determines if thecall, signal, trigger or command directed to and received by SLSplatform 115 at block 502 prompts the SLS platform 115 that a “next setof instructions” associated with a reserved relationship number is needto be performed. If not, then the call, signal, trigger or commanddirected to and received by SLS platform 115 at block 502 receivesalternate processing at block 514. The alternate processing of 514 isnot within the scope of this disclosure. If the call, signal, trigger orcommand directed to and received by SLS platform 115 at block 502 doesprompt the SLS platform 115 that a “next set of instructions” associatedwith a reserved relationship number is need to be performed then the“yes” branch is followed to block 516. Notably, it is envisioned by thisdisclosure that the SLS platform 115 may be able to perform block 512using information included within the call, signal, trigger or commanddirected to and received by SLS platform 115 at block 502. Moreover, itis envisioned by this disclosure that the SLS platform 115 may be ableto perform block 512 through previous programming, information, oralgorithms stored within the SLS platform 115. It is also envisioned bythis disclosure that the SLS platform 115 may be able to perform block512 through communication with third party entities, elements,computers, software, hardware, etc. using communications network 125.

Additionally, it is envisioned by this disclosure that performance ofblock 512 may involve one or multiple steps and that these steps mayinvolve one or more pieces of hardware/software separate and distinctfrom the SLS platform 115. Those of ordinary skill in the art willrecognize that, depending on the nature of the call, signal, trigger orcommand directed to and received by SLS platform 115 at block 502,multiple components of the SLS platform 115 and/or other communicativelycoupled pieces of hardware may be used.

At block 516, the SLS platform 115 queries the central SLS database 116for the reserved relationship number that maps to the combination of thesubscriber's SLS phone number and the “next set of instructions”determined at block 512. At block 518, a call is established between theSLS platform 115 and the subscriber TD 110. In some non-limitingembodiments of block 518, the SLS platform 115 initiates the callthrough the communication network 125's voice channel with thesubscriber TD 110 by dialing its primary phone number from the reservedrelationship number of block 516. In other non-limiting embodiments ofblock 518, the subscriber's TD 110 initiates the call through thecommunication network 125's voice channel with the SLS platform 115 bydialing the reserved relationship number of block 516 from thesubscriber TD 110's primary phone number after receiving a datacommunication from the SLS platform 115 with information containing thereserved relationship number of block 516 and instructions to initiatethe call. It is envisioned that in some embodiments of block 518 an SLSmodule 105 may recognize that an incoming call is from the SLS platform115 by virtue of the call originating from a reserved relationshipnumber.

Although not depicted in FIG. 5B, after block 518 the SLS module 105queries the local SLS database 106 for the “next set of instructions”that maps to the combination of the reserved relationship number fromwhich the SLS platform 115 directed the call and the subscriber's SLSphone number. The SLS module 105 then performs the “next set ofinstructions” previously queried. As a non-limiting example, the SLSmodule 105 may perform all the steps, functions, processing, etc.related to the “next set of instructions” “inform the TD that avoicemail is waiting”.

Certain steps or blocks in the processes or process flows described inthis specification naturally precede others for the invention tofunction as described. However, the invention is not limited to theorder of the steps or blocks described if such order or sequence doesnot alter the functionality of the invention. That is, it is recognizedthat some steps or blocks may performed before, after, or parallel(substantially simultaneously with) other steps or blocks withoutdeparting from the scope and spirit of the invention. In some instances,certain steps or blocks may be omitted or not performed withoutdeparting from the invention. Also, in some instances, multiple actionsdepicted and described as unique steps or blocks in the presentdisclosure may be comprised within a single step or block. Further,words such as “thereafter”, “then”, “next”, “subsequently”, etc. are notintended to limit the order of the steps or blocks. These words aresimply used to guide the reader through the description of the exemplarymethod.

Additionally, one of ordinary skill in programming is able to writecomputer code or identify appropriate hardware and/or circuits toimplement the disclosed invention without difficulty based on the flowcharts and associated description in this specification, for example.Therefore, disclosure of a particular set of program code instructionsor detailed hardware devices is not considered necessary for an adequateunderstanding of how to make and use the invention. The inventivefunctionality of the claimed computer implemented processes is explainedin more detail in the above description and in conjunction with theFigures which may illustrate various process flows.

In one or more exemplary aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted as one or more instructions or code on a computer-readablemedium. Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another.

A storage media may be any available media that may be accessed by acomputer. By way of example, and not limitation, such computer-readablemedia may comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium that may be used to carry or store desired program code inthe form of instructions or data structures and that may be accessed bya computer.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (“DSL”), or wireless technologies such asinfrared, radio, and microwave, then the coaxial cable, fiber opticcable, twisted pair, DSL, or wireless technologies such as infrared,radio, acoustic and microwave are included in the definition of medium.

Disk and disc, as used herein, includes compact disc (“CD”), laser disc,optical disc, digital versatile disc (“DVD”), floppy disk and blu-raydisc where disks usually reproduce data magnetically, while discsreproduce data optically with lasers. Combinations of the above shouldalso be included within the scope of computer-readable media.

Therefore, although selected aspects have been illustrated and describedin detail, it will be understood that various substitutions andalterations may be made therein without departing from the spirit andscope of the present invention, as defined by the following claims.

What is claimed is:
 1. A system that provides a requested service to asubscriber of a second line service (“SLS”), the system comprising: aprocessor; a memory element communicatively coupled to the processor; aninterface to a circuit switched network communicatively coupled to theprocessor; the processor, in response to commands obtained from thememory element, operative to: select a reserved relationship number,wherein the reserved relationship number consists only of a validnetwork terminable number that is recognized by the circuit switchednetwork as being a number to be processed by the system and, wherein thereserved relationship number does not include any other information orany prefix or suffix; associate the relationship number with (1) an SLSphone number of an originating terminal device (OTD), wherein theoriginating OTD is communicatively coupled to the interface of thesystem through the circuit switched network and wherein the OTD has aprimary number serviced by a mobile service provider and is provisionedwith the SLS and has at least one SLS phone number assigned there to,(2) at least one service and (3) the primary phone number of the OTD;create a database entry for the association; transmit the reservedrelationship number to the OTD; receive a communication request that isinvoked by the OTD initiating the communication to the reservedrelationship number, wherein the communication request is transmittedwithout the inclusion of a calling line identification of the OTD;select an entry from a database, wherein the entry is selected based onthe received reserved relationship number, and wherein the entryidentifies the primary phone number of the OTD, a particular SLS numberassigned to the OTD and the service; and initiate the provision of theservice, such service being rendered to the requesting OTD and beingattributed to the particular SLS phone number.
 2. The system of claim 1,wherein the received communication request is a call setup request andthe processor is operative to select a particular service for thereserved relationship number, the primary phone number of the OTD andthe particular SLS number assigned to the OTD based on the receivedcommunication request being a call setup request.
 3. The system of claim2, wherein the processor initiates the provision of the service bycommunicatively connecting the OTD to a voicemail system for retrievingvoicemail messages.
 4. The system of claim 2, wherein the processorinitiates the provision of the service by communicatively connecting theOTD to a third party phone number and using the particular SLS of theOTD as the calling line identifier.
 5. The system of claim 2, whereinthe processor initiates the provision of the service by providing amessage to the OTD regarding the status of received voicemail messages.6. The system of claim 1, wherein the received communication request isa text message and the processor is operative to select a particularservice for the reserved relationship number, the primary phone numberof the OTD and the particular SLS number assigned to the OTD based onthe received communication request being a text message.
 7. The systemof claim 6, wherein the processor initiates the provision of the serviceby communicatively connecting the OTD to a voicemail system forretrieving voicemail messages.
 8. The system of claim 6, wherein theprocessor initiates the provision of the service by sending the textmessage to a third party phone number and using the particular SLS ofthe OTD as the originating identifier.
 9. The system of claim 6, whereinthe processor initiates the provision of the service by providing a textmessage to the OTD regarding the status of received voicemail messages.10. A telecommunications service platform that provides a requestedservice to a subscriber of a second line service (“SLS”), thetelecommunications service platform comprising: a processor; a memoryelement communicatively coupled to the processor; an interface to acircuit switched network communicatively coupled to the processor; theprocessor, in response to commands obtained from the memory element,operative to: provision an SLS provisioned telecommunications device(“TD”), wherein the TD has a primary number serviced by a mobile serviceprovider and an SLS number for receiving a particular service, by:selecting the particular service to be rendered; selecting arelationship number to be associated with the particular service,wherein the relationship number consists only of a valid networkterminable number that is recognized by the circuit switched network asbeing a number to be processed by the telecommunications serviceplatform, wherein the relationship number does not include any otherinformation or any prefix or suffix; associating the relationship numberand the particular service with the SLS number and the primary number ofthe TD; and creating a database entry for the association; establish acommunication path to the TD; communicate the reserved relationshipnumber to the TD; receive a communication request from the TD, thecommunication request being initiated by the TD initiating thecommunication directed to the relationship number, wherein thecommunication request is received by the telecommunications serviceplatform without the inclusion of any additional information; identifythe particular service, the primary number, and the particular SLS phonenumber associated with the relationship number; identify one or moreactions associated with the particular service; and perform the one ormore actions on behalf of the TD and associating the service with theSLS phone number of the TD.
 11. The telecommunications service platformof claim 10, wherein the received communication request is a call setuprequest initiated by dialing the relationship number using the TD, andthe processor is operative to select a particular service for therelationship number, the primary phone number of the OTD and theparticular SLS number assigned to the OTD based on the receivedcommunication request being a call setup request.
 12. Thetelecommunications service platform of claim 11, wherein the processorinitiates the provision of the service by communicatively connecting theOTD to a voicemail system for retrieving voicemail messages.
 13. Thetelecommunications service platform of claim 11, wherein the processorinitiates the provision of the service by communicatively connecting theOTD to a third party phone number and using the particular SLS of theOTD as the calling line identifier.
 14. The telecommunications serviceplatform of claim 11, wherein the processor initiates the provision ofthe service by providing a message to the OTD regarding the status ofreceived voicemail messages.
 15. The telecommunications service platformof claim 10, wherein the received communication request is a textmessage and the processor is operative to select a particular servicefor the reserved relationship number, the primary phone number of theOTD and the particular SLS number assigned to the OTD based on thereceived communication request being a text message.
 16. Thetelecommunications service platform of claim 15, wherein the processorinitiates the provision of the service by communicatively connecting theOTD to a voicemail system for retrieving voicemail messages.
 17. Thetelecommunications service platform of claim 15, wherein the processorinitiates the provision of the service by sending the text message to athird party phone number and using the particular SLS of the OTD as theoriginating identifier.
 18. The telecommunications service platform ofclaim 15, wherein the processor initiates the provision of the serviceby providing a text message to the OTD regarding the status of receivedvoicemail messages.
 19. A telecommunications platform that provides asecond line service (“SLS”) special operation to an SLS provisionedterminal device (TD), wherein the first TD has at least one SLS phonenumber assigned therewith, the telecommunications platform comprising: aprocessor; a memory element communicatively coupled to the processor; aninterface to a circuit switched network communicatively coupled to theprocessor; the processor, in response to commands obtained from thememory element, operative to: select a reserved relationship number,wherein the reserved relationship number consists only of a validnetwork terminable number that is recognized by the circuit switchednetwork as being a number to be processed by the system and, wherein thereserved relationship number does not include any other information orany prefix or suffix; associate the relationship number with (1) an SLSphone number of an originating terminal device (OTD), wherein theoriginating OTD is communicatively coupled to the interface of thesystem through the circuit switched network and wherein the OTD has aprimary number serviced by a mobile service provider and is provisionedwith the SLS and has at least one SLS phone number assigned there to,(2) at least one service and (3) the primary phone number of the OTD;create a database entry for the association; transmit the reservedrelationship number to the OTD; receive a call initiation request thatis invoked by the OTD dialing the relationship number, wherein the callinitiation request is transmitted without the inclusion of a callingline identification of the OTD or any prefix or suffix; select an entryfrom a database, wherein the entry is selected based on the receivedreserved relationship number, and wherein the entry identifies theprimary phone number of the OTD, a particular SLS number assigned to theOTD and the service; and initiate the provision of the service, suchservice being rendered to the requesting OTD and being attributed to theparticular SLS phone number, wherein the service is selected form agroup of services including (a) placing a call to a third party andidentifying the originator as the SLS phone number of the OTD, (b)connecting the OTD to voicemail and (c) providing a message to the OTDregarding the status of received voice messages.